home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 6
/
The Arsenal Files 6 (Arsenal Computer).ISO
/
os2bbs
/
mxl220.zip
/
MAXLIST.DOC
< prev
next >
Wrap
Text File
|
1996-02-17
|
60KB
|
1,449 lines
┌╦═══════════════════════════════════════════════════════════════════ ┌╦═══╦┐
│║ ┌╦ ╦┐┌╦ ╦┐┌╦═╦═╦┐┌╦═╦═╦┐┌╦ ┌╦═══╦┐ ┌╦══╦┐ ┌╦══╦┐ │║ ╩┘
└╩═══╦┐├╬═══╬┤│║ ║│ ║ ║ │║ ├╬══ │╠══╩╦┐│╠══╩╦┐└╩═══╦┐
┌╦ ║│└╩ ╩┘└╩═══╩┘ ╩ ╩ └╩═══╩┘└╩═══╩┘ └╩═══╩┘└╩═══╩┘ ║│
└╩═══╩┘ ════════════════════ H A T T I N G E N ══════════════════════════╩┘
▓▒░ ─────────────────────────────────────────── ░▒▓
▓▒░─────────────▓▒░ HOME OF MAXLIST FILELISTPROCESSOR ░▒▓─────────────░▒▓
▓▒░ ─────────────────────────────────────────── ░▒▓
═══════════════════════════════════════════════════════════════════════════
▓▒░ ░▒▓
▓▒░ ┌──────┐ ┌──────┐ ┌─┐ ┌─┐ ┌─┐ ┌─┐ ┌──────┐ ┌───────┐ ░▒▓
▓▒░ └──────┘ └──────┘ └─┘ └─┘ └─┘ └─┘ └──────┘ └───────┘ ░▒▓
▓▒░ ┌─┐┌┐┌─┐ ┌──────┐ ┌──┐ ┌─┐ ┌─┐ ┌──────┐ ┌─┐ ░▒▓
▓▒░ │ │└┘│ │ │ ┌──┐ │ ┌┘┌┐└┐ │ │ │ │ └────┐ │ │ │ ░▒▓
▓▒░ │ │ │ │ │ │ │ │ ┌┘┌┘└┐└┐ │ └────┐ │ │ ┌────┘ │ │ │ ░▒▓
▓▒░ └─┘ └─┘ └─┘ └─┘ └─┘ └─┘ └──────┘ └─┘ └──────┘ └─┘ ░▒▓
▓▒░ Template controlled Filebaseprozessor for Maximus Systems ░▒▓
▓▒░ Version 2.20 Copyright 1994-96 by Wilfried Brinkmann ░▒▓
▓▒░ ░▒▓
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ All rights reserved ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
═════════════════════════════════════════════════════════════════════════════
─╥────┐ ╓──┐ ╓──┐ ╥ ┬ ╓─╥─┐ ╥──┐ ╓──┐ ╓─╥─┐ ╓──┐ ╓─╥─┐ ─╥─ ╓──┐ ╓──┐
║ │ ║ │ ║ ║ │ ║ ║ │ ╟─ ║ │ ║ ╟──┤ ║ ║ ║ │ ║ │
║ │ ╙──┘ ╙──┘ ╙──┘ ╨ ╨ ┴ ╨──┘ ╨ ┴ ╨ ╨ ┴ ╨ ─╨─ ╙──┘ ╨ ┴
║ │ ───────── MaxList Version 2.20 Dos, DPMI and OS/2 ─────────
─╨────┘
┌───────────────────╖
│ Importend note !! ╠════════════════════════════════════════════════════════
╘═══════════════════╝
I have invested SO MUCH time and work for this program. Please honor
my work and send me a 'freewilling' gift as you want.
For the last year, it has shown, only a few Sysops are ready to honor
my work. Therefore the following hint:
It's in your hand, if MaxList still keeps 'Requestware' !
▓▒░─────────────────────────────────────────────────────────────────░▒▓
▓▒░ Adress: Bank-Account: ░▒▓
▓▒░ Wilfried Brinkmann Genossenschafts-Bank Essen eG ░▒▓
▓▒░ Im Tal 136 BLZ: 360 604 88 ░▒▓
▓▒░ 45529 Hattingen (Germany) KTO: 114 713 501 ░▒▓
▓▒░─────────────────────────────────────────────────────────────────░▒▓
┌──────────╖
│ Warranty ╠═════════════════════════════════════════════════════════════════
╘══════════╝
No warranty is taken for this software, neither expressed or implied,
especially for correct function or usability for a certain purpose.
The author is not responsible for any damages caused by the usage of
this software. YOU as user of MaxList carry the full risk for usability
and reliability.
The only warranty I can give is that this program will consume some
space on your hard disk.
I will try my best to remove errors I am informed about, as far as I
get enough information on an error.
IF YOU DO NOT AGREE WITH THESE CONDITIONS, YOU MUST NOT USE THIS PROGRAM!
┌─────────────────────────────╖
│ Support in case of problems ╠══════════════════════════════════════════════
╘═════════════════════════════╝
VOICE-SUPPORT:
Call +49-2324-42350 and get help free of charge.
You may call this number daily between 10:00 and 22:00 MET/MEST, but
take into consideration, that I will not always be there.
NETMAIL-SUPPORT:
Send me a netmail with your questions. You may avoid eventual
check-back, when you include the relevant parts of your configuration
file.
Answers will normally be sent a routed netmail. Crashmail is only used
in exceptional cases.
You will reach me in FidoNet at 2:2444/2050, OS2Net at 81:449/2025
and Internet (wilfried.brinkmann@shuttle.mediaserve.de)
HINT!
For additional Supportnodes please read the file REGISTER.TXT
┌─────────╖
│ Credits ╠══════════════════════════════════════════════════════════════════
╘═════════╝
I want to express my thank to all who have tested MaxList on a
voluntary basis and detailly reported errors and gave constructive
improvement suggestions. Without their help MaxList would not have
been that successful.
┌─────────────────╖
│ Copyright Notes ╠══════════════════════════════════════════════════════════
╘═════════════════╝
The following names, programs and products are mentioned in this
documentation and are protected by law:
4OS2 JP Software Inc.
Binkley Bit Bucket Software Co.
CantaLoup Buenter Communucations
Borland Borland International Inc.
Maximus, Squish Scott J. Dudley
MS-DOS Microsoft Corporation
OS/2 IBM Corporation
PkZip PKWARE Inc.
┌───────────────────╖
│ Common Directions ╠════════════════════════════════════════════════════════
╘═══════════════════╝
The format of EVERY filelist and EVERY FILES.BBS is controlled
without execption by the configured TEMPLATES.
These templates contain all instructions how MaxList will handle
and format the data contained in your filebase.
In either case you should therefore carefully read the TEMPLATE.DOC
before modifying the configuration files.
MaxList uses the FILEAREA.CTL file of Maximus to generate the file
lists. Additional control files may be included there by using the
INCLUDE statement of Max.
MaxList can create announcelists. It compares each file with the
Maximus index (MAXFILES.IDX) to check if this file exist in filebase.
MaxList supports archiver programs directly. This means that the
generated file lists are packed automatically, without user
intervention. The parameters needed for the archivers are defined in
the file COMPRESS.CFG, which has the same format as those used by
Maximus and Squish.
MaxList is able to add orphan files automatically to the file lists
and/or the FILES.BBS (Keyword AddOrphanFiles). When the orphan file
contains a FILE_ID.DIZ, this one will be used for the description.
Furthermore a (small) editor is integrated in MaxList, letting you
manually insert file descriptions for orphan files. The descriptions
may also be taken from a FILE_ID.DIZ in this case.
MaxList supports long OS/2 HPFS file- and pathnames. Only one
restriction exists: these names may not contain blanks.
NOTE:
The files of your filebase (those contained in your FILES.BBS)
must have names following the DOS 8.3 convention. Long names
are not supported here.
The date to be shown in the lists can either be the "LastWriteDate"
(DOS) or the "FileCreationDate" (OS/2 HPFS only!)
┌─────────────────────────────────────────────────────────╖
│ Syntax being used in configuration, wildcard characters ╠══════════════════
╘═════════════════════════════════════════════════════════╝
Parameters which may no be omitted are represented in pointed
parentheses, e.g. <Area>, optional parameters are represented by
brackets, e.g. [Option]
Most parameters may contain wildcard characters (? and *).
Area tags may be given as range, e.g. 100..200.
NOTE: When using the range format, wildcards are not allowed!
Area parameters may be given as area tags as well as a combination of
group and area.
If you have the group GFD.APP and inside it the area with tag TOOL,
you may use GFD.APP.TOOL to name this area. Of course you may use
wildcards here. For example the parameter GFD.ALL.* will tell to use
all areas following after GFD.APP; the area GFD.APP.ARC.XYZ will
match this parameter.
Maximus AccessLevel and keys are handled seperately for each area or
group. Wildcards are allowed. Using xxACS */P will match all
areas/groups containing a P in the key list (e.g. Normal/ACPX).
┌───────────────────────╖
│ Newfiles announcement ╠════════════════════════════════════════════════════
╘═══════════════════════╝
MaxList is capable to create announcelists and write this as a Echomail
directly to your Squish mailbase.
If a list is greater than 32 Kbytes, this is splitted in more mails.
The Subjectline is expanded with a 'Page/Pages' notice, e.g. [1/4].
At the end of message the string '>Continue on next page<' is inserted
and also at top of next page the string '>Continue from previouse page<'.
All messageparameters (Your AKA, From, To, Subject and Origin) is full
controlled by you. For more info about this, see 'SQUISHMAIL'.
MaxList can also create a 'Echtoss' logfile for your tosser.
For more info, see 'EchoTossLog'.
To find out if a file is 'new', MaxList compares each file with the
Maximus index (MAXFILES.IDX). Is the file not found, then this will be
written to the announcelist.
Every time you starts MaxList, this list is deleted. A new list is
created only, when one or more new files will be found.
When you starts FB(p) after each run of MaxList, then you have the
warranty, that only 'new' files resides in announcelist.
Hint:
─────
Areas with TYPE CD or DATELIST are never scanned.
MaxList can't create a new Squishbase! The Squishecho, which is used
for announcemails must exist on your system.
┌──────────────────────────────────────────────────────╖
│ Controlling flow by using IF / IFN, ELSEIF and ENDIF ╠═════════════════════
╘══════════════════════════════════════════════════════╝
IF <expression> resp. IFN <expression> may be involved as you like,
e.g.:
IF <expr>
...
IF <expr>
...
ENDIF
...
ENDIF
The following internal expressions are available:
DOS - True, when MaxList is running under DOS or a VDM
OS2 - True, when MaxList is running under OS/2
IMPORT - True, when command line parameter -I was specified
SPECIAL - True, when command line parameter -S was specified
DUPECHECK - True, when command line parameter -D was specified
In addition you may define your own variables and use these in an
expression. The variables can be set by the DEFINE statement or are
tried to be resolved from the programs environment (so you may define
environment variables before starting MaxList and access these from
within MaxList!)
NOTE: Contens of variables are case sensitive!
Example:
────────
IF TestVar Yes - True, when TestVar contains Yes
IFN TestVar Yes - True, when TestVar does NOT contain Yes
IF TestVar YES - False, when TestVar contains Yes (casesensitive)
The switches DOS and OS2 can also stand in front of each keyword.
This line is processed only, if <switch> true.
Example:
────────
DOS Execute &D:\MAX\FB.EXE
OS2 Execute &D:\MAX\FBP.EXE
┌──────────────────────────────────────────╖
│ Including additional configuration files ╠═════════════════════════════════
╘══════════════════════════════════════════╝
Using INCLUDE <d:\path\filename.ext> tells MaxList to include additional
configuration parts at this place. Up to 10 levels of inludes are
supported (i.e. the included file contains again a INCLUDE).
┌────────────────────────────────────╖
│ Command line parameters of MaxList ╠═══════════════════════════════════════
╘════════════════════════════════════╝
MaxList recognizes several (optional) parameters at its command line.
All parameters may be used simultaneously, no matter of the order.
The parameters are detected by the leading slash (/) or dash (-).
/C, -C specify alternative configuration file
Usage: MAXLIST(P) -Cd:\path\config.ext
/D, -D activate dupe checking
Usage: MAXLIST(P) -D
MaxList includes the possibility to check your file base for dupes.
When -D is specified, the internal switch DUPECHECK is set to true
and may be used in an IF / IFN expression.
The way how a dupe check is performed may be set by keyword DUPECHECK
in the configuration file. In addition the definition for a file list
DUPE must be present, otherwise NO dupe check will be done!
/S, -S switch to special mode
Usage: MAXLIST(P) -S
MaxList has a special mode. When it is active, the internal switch
SPECIAL is set to true and may be used in an IF / IFN expression.
The original intention for this option was to give an easy way to
generate file lists for a filebase laying on CD-ROM. As this one is
normally not modified, or if you have several CD-ROMs, you may use
this to create the file list for a CD-ROM by starting MaxList with
option -S. I have defined the CD-ROM file list definition within an
IF SPECIAL ... ENDIF block and exluded the areas on CD-ROM by
IFN SPECIAL and NOPROCESS for normal processing.
/I, -I switch to automatic import mode for descriptions
Usage: MAXLIST(P) -I[=Area[..Area]]
When this option is specified, MaxList will import the description
for ALL files of your filebase from a FILE_ID.DIZ in the archive.
Optional you may restrict this function to some areas by adding an
area or an =area..area directly behind the -I. When using =area,
wildcards are allowed.
You may specify the areas to exclude from this processing also by
using the keyword IMPORT in the configuration.
/M, -M manual description import
Usage: MAXLIST(P) -M
This option activate the (small) internal editor of MaxList, and also
the choosen editor under the token 'ExternEditor'.
When no FILE_ID.DIZ is found in AddOrphanFiles mode, you may enter a
(up to 10 lines long) description for the corresponding file.
Is a FILE_ID.DIZ found, the external editor is started with this file.
/?, -?, ? MaxList help
Usage: MAXLIST(P) -?
Will give you a short description of all command line parameters.
┌────────────────────────────────────────╖
│ MaxLists integrated description editor ╠═══════════════════════════════════
╘════════════════════════════════════════╝
MaxList contains a simple editor for adding file descriptions manually
in AddOrphanFiles mode, when no FILE_ID.DIZ was found in an archive.
Editing existing file descriptions is only possible, you have used the
token 'ExternEditor'
The editor will start automatically when command line parameter -M
was given. The following keys are supported in the editor:
cursor keys Up, Down, Left, Right - moves the cursor
Pos1 or Home - move cursor to start of line
End - move cursor to end of line
PageUp (PgUp) - move cursor to first line
PageDown (PgDn) - move cursor to last line
Strg-N or Ctrl-N - insert a blank line
Strg-Y or Ctrl-Y - delete line
Del - delete character at cursor
BS (Backspace) - delete characted left to cursor
F2 - save and exit
F3 - save and add description as
FILE_ID.DIZ to the archive
ESC - cancel
When the description is saved by F3, MaxList will try to add the desc
as file FILE_ID.DIZ to the archive. The date of the FILE_ID.DIZ is set
to the date of the archive in this case.
When no description is entered, or the editor is canceled by ESC, the
string defined by keyword NODESCRIPTION is written to the FILES.BBS.
┌────────────────────────────────────╖
│ Full path names in FILES.BBS files ╠═══════════════════════════════════════
╘════════════════════════════════════╝
MaxList recognizes files with a path in the FILES.BBS files and processes
them correctly. This has no effects the length of the description.
(BTW: Maximus is also able to handle such entries correctly).
The path of the file will nor occur in the file list. Only the filename
will be present here.
┌─────────────────────────╖
│ MaxList and Maximus 3.0 ╠══════════════════════════════════════════════════
╘═════════════════════════╝
MaxList is able to cooperate with EVERY version of Maximus.
It will silently ignore unknown Maximus instructions.
The TYPE instruction of Maximus 3.0
───────────────────────────────────
MaxList supports a special form of FILES.BBS, which is defined by
TYPE DATELIST at Maximus 3.0. This FILES.BBS contains file date and size
in addition to the usual entries.
When you have defined an area as TYPE DATELIST in your FILEAREA.CTL,
MaxList will not try to evaluate file size and date from the file, but
use the given values instead. The data in the FILES.BBS is converted to
the internal format n you have defined an area as TYPE DATELIST in your
FILEAREA.CTL, MaxList will not try to evaluate file size and date from
the file, but use the given values instead. The data in the FILES.BBS is
converted to the internal format and will be put in the file list as
specified in the corresponding TEMPLATE. MaxList expects the file size
after the filename, followed by the file date. The file size is ALWAYS
expected in bytes.
You need to define a special template for FILES.BBS following TYPE
DATELIST format. Additional information on this topic is located in
TEMPLATE.DOC.
When the file size and date is MISSING, MaxList will evaluate them from
the file directly. In this special case MaxList behaves as if no TYPE
DATELIST was found.
Areas marked as TYPE DATELIST will NEVER be processed for RemoveOffline
and RemoveOldFile. The flags for the age of a file are brought up to date
every time MaxList runs.
═════════════════════════════════════════════════════════════════════════════
╓─────┐ ╓──┐ ╓──┐ ╥──┐ ─╥─ ╓──┐ ╥ ┬ ╥──┐ ╓──┐ ╓─╥─┐ ─╥─ ╓──┐ ╓──┐
║ ║ │ ║ │ ╟─ ║ ║ ─┐ ║ │ ╟─┬┘ ╟──┤ ║ ║ ║ │ ║ │
║ ╙──┘ ╨ ┴ ╨ ─╨─ ╙──┘ ╙──┘ ╨ ┴ ╨ ┴ ╨ ─╨─ ╙──┘ ╨ ┴
║ ──────── MaxList Version 2.20 Dos, DPMI and OS/2 ────────
╙─────┘
┌────────────────────────────────────╖
│ Your Name and Key for Registration ╠═══════════════════════════════════════
╘════════════════════════════════════╝
┌─────────
│ UserName "Your Name"
└──────────────────────────
Here you must enter your name as given in registration
UserName "John Doe"
┌───────
│ RegKey <Hexadecimal keycode>
└────────────────────────────────────
Here you must enter your Keycode as given in registration
RegKey 1234567890ABCDEF1234567890ABCD
┌───────────────────────────────────╖
│ Assignment of Variables by DEFINE ╠════════════════════════════════════════
╘═══════════════════════════════════╝
┌───────
│ Define <Name_of_Variable> <Value>
└──────────────────────────────────────
Multiple usage possible
Via DEFINE you can assign a free value to a variable. The name of the
variable is free, too. You may then access the value, equivalent to
accessing environment variables, later on in the configuration.
When MaxList will find a string enclosed in a percent sign (e.g %TEST%),
the whole string will be substituted by the value of that variable.
Define ListDir E:\Listen
Define MxLDir D:\FileList
Define Template %MxLDir%\Template
Define Font %MxLDir%\Font\digi3x5.fnt
Define Flags D:\BINK\FLAGS
Define Task1 %Flags%\Task.01
Define Task2 %Flags%\Task.02
Define Task3 %Flags%\Task.03
Define Task0 %Flags%\Task.00
Define TaskMax1 %Flags%\Maximus.01
Define TaskMax2 %Flags%\Maximus.02
Define TaskMax3 %Flags%\Maximus.03
┌──────────────────────╖
│ Archiver Definitions ╠═════════════════════════════════════════════════════
╘══════════════════════╝
MaxList uses an ascii file for defining the archiver parameters and more.
This file is 100% compatible to that one used by Squish and Maximus.
Include %MxlDir%\archiver.cfg
┌─────────────────────────╖
│ Start External Programs ╠══════════════════════════════════════════════════
╘═════════════════════════╝
┌────────
│ Execute [& | ^]<programm [parameter]>
└───────────────────────────────────────
Multiple usage possible
Using the Execute command you can tell MaxList to start any external
programs after all file list processing is completed.
When the program name is preceded by an "&", MaxList will change the
current path to that of the program before starting it.
In addition you can place a "^" in front of the command line, this will
redirect all output to NUL (i.e. suppress display of program output).
User of OS/2 may use the 'START "WinTitle" /FG ...' command for starting
programs. If you do not like to have the whole string in the log file,
you may exclude the parts you don't want to see by putting them in
brackets []:
[Start "FBP" /FG /C /Pos=1,1,25,80] &D:\MAX\FBP.EXE
The log will only contain "Call D:\MAX\FBP.EXE" then.
ifn DupeCheck
if OS2
Execute &D:\MAX\FBP.EXE
Execute &D:\MAX\OKF.EXE Dupe
EndIf
EndIf
┌─────────────────╖
│ Global Settings ╠══════════════════════════════════════════════════════════
╘═════════════════╝
┌───────
│ Debugg <Yes | No>
└─────────────────────────────
This is for testing purposes.
When Debugg = Yes, MaxList will NOT alter any FILES.BBS. Instead, it
will generate a FILES.$$$, where you can check how the FILES.BBS files
are processed and how it would look like. If you set Debugg to No again,
the temporary FILES.$$$ files again are automatically deleted.
Debugg Yes
┌────────────
│ WaitIfError <Yes | No>
└─────────────────────────────
MaxList will wait for any key to be pressed when any error occurs, if
this is set to Yes. In case of error the "SemaphoreRun" will be deleted
(so that other programs will not wait unnecessarily) and all time slices
are released.
WaitIfError Yes
┌───────────────
│ RedirectOutput <Yes | No>
└─────────────────────────────
If set to Yes, MaxList will redirect the output of an archiver to NUL
(e.g. when importing the FILE_ID.DIZ).
RedirectOutput Yes
┌─────────────────
│ UseFileDivisions <Yes | No>
└─────────────────────────────
If you use Maximus 3.0, you probably use the new feature to build file
divisions. If you like to get a "flat" file list, i.e. without grouping
areas into divisions, you have to specify No here.
For Maximus 2.XX users, this keyword will have no effects.
UseFileDivision Yes
┌─────────────────
│ UseFCreationDate <Yes | No>
└─────────────────────────────
When you use HPFS in OS/2, you have the choice to select from two kind of
file dates: "LastWriteDate" -> No, "FileCreationDate" -> Yes.
The file date you select here will be printed in the lists and it is used
for new files check.
NOTE
On a FAT file system, du NOT use this parameter, otherwise all time
and date distributions are damaged !
UseFCreationDate No
┌─────────────────
│ MainGroupAtFront <Yes | No>
└─────────────────────────────
When you have file divisions active, but use some areas which are not
within any file division, you can set here wether to put these areas to
top of the lists (Yes) or to the end (No).
MainGroupAtFront No
┌───────────
│ AddComment <Yes | No>
└─────────────────────────────
Comments contained in FILES.BBS files are supressed in the file lists,
if you specify NO here. The command will have no effect on the FILES.BBS
files. MaxList recognizes comments following the next two rules:
a) first char of a line is a dash (-) or
b) first line is blank (only CrLf at start), followed by lines that
have at least one blank as first character and a last line (before
next file name), that is a blank line again (CrLf at start of line).
Example:
a) FILE1.EXT This is the first file
- ═════════════
- Comment
- ═════════════
FILE2.EXT This is the second file
b) FILE1.EXT This is the first file
═════════════
Comment
═════════════
FILE2.EXT This is the second file
Dashes (-) in comment lines are substituted by blanks in the file lists,
if they are not followed by another dash.
AddComment Yes
┌──────────────
│ UseMaxHomeDir <Yes | No>
└─────────────────────────────
If a relative path is specified in your FILEAREA.CTL file behind the
keywords DOWNLOAD or FILELIST, i.e. a pathname WITHOUT a drive letter,
MaxList is able to extend this by using the path to the first
FILEAREA.CTL file.
If you specified MaxAreaFile D:\MAX\FILEAREA.CTL in this config, MaxList
will extend the entry DOWNLOAD BBS\LISTS to D:\MAX\BBS\LISTS, if
UseMaxHomeDir is set to Yes.
UseMaxHomeDir No
┌──────────
│ DLCounter <String>
└───────────────────────────
If the token @DlCounter is used in a template, MaxList will replace it by
the string you specify here, if none is present in the FILES.BBS.
An existing download counter is not changed.
Furthermore, this entry is needed to remove existing download counters.
When a FILES.BBS contains a download counter, but the template does not
have a @DLCOUNTER token, MaxList will remove it, when it uses the frame
characters of the string specified here.
For additional information see TEMPLATE.DOC.
DLCounter [00]
┌─────────
│ FlagChar <days, character> <days, character> ..
└──────────────────────────────────────────────────────────
For emphasizing new files you may specify several flags here.
When a file is newer than <days>, the specified flag character is used.
Between each pair of <days, character> you have to put at least one blank.
FlagChar 7,√ 14,* 30,+
┌─────────────────
│ BBSWildcardFiles <ALL | NEW>
└──────────────────────────────
In a FILES.BBS file names may contain wildcard characters.
In that case, MaxList will either list all files matching <ALL> or only
the newest file <NEW>.
The FILES.BBS is not changed, the wildcards stay in it.
NOTE
A FILES.BBS of TYPE DATELIST must not contain any wildcard character.
If one is found, it will be placed AS IS into the file lists!
BBSWildCardFiles All
┌──────────────
│ NoDescription <String>
└───────────────────────────
<String> will be used for files where no description is available.
It may not exceed 255 characters in length.
NoDescription <No description available>
┌────────
│ OffLine <String>
└───────────────────────────
<String> will be used for entries in a FILES.BBS where the corresponding
file is missing. This is only done, if you specified to do so in the
template file. For further information see TEMPLATE.DOC, @OFFLINE.
The length of this string should not exceed 17 characters.
OffLine <offline>
┌────────
│ LogFile <d:\path\filename.ext>
└─────────────────────────────────────────
Path and name of logfile.
When no LogFile is specified, no log will be written at all.
LogFile MAXLIST.LOG
┌─────────
│ LogLevel <Num>
└────────────────────────
LogLevel has to be in the range 1..3. 3 is the highest level, containing
the maximum of information.
LogLevel 2
┌────────
│ DayName <String String ... String>
└─────────────────────────────────────
Use this to translate names of days into a local language.
Default is in english. The first string is the name for sunday, second
monday and so on. All days must be on one line, separated by at least
one blank. Every name may consist of up to 10 chars.
DayName Sunday Monday Tuesday Wednesday Thursday Friday Saturday
┌──────────
│ MonthName <String String ... String>
└───────────────────────────────────────
Same procedure for the (abbrevated) names of months.
These may be used in the templates then (MMM). Starts with January,
every name max. 3 chars in length and separated by at least one blank.
MonthName Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
┌─────────
│ LoadFont <d:\path\Filename.ext>
└─────────────────────────────────────────
Multiple usage possible
This instruction tells MaxList to load a font file. The font defined
within one file may then be used in the templates. Every font is
identified by a unique name (max. 8 chars), so MaxList knows which one
to use.
To create your own fonts, use FNTMAKE(p).EXE (v1.20), which will by found
in archive FONTS.ZIP.
Please do not forget to send the good ones to the author of MaxList ;)
For detailed instructions how to use a font, see TEMPLATE.DOC,
topic @FONTSTR
LoadFont %Font%
┌──────────
│ DupeCheck <NAME | NAME.EXT>
└────────────────────────────────────
MaxList comes with a builtin dupe checking routine.
To use it, a file list of type DUPE has to be configured. In this list
MaxList will then place all dupes found, according to the template file.
As for every other list, it is possible to use Exclude and Include in the
dupe list config.
This entry now defines, HOW MaxList will check for dupes.
<NAME> will check only the name of the files, without extension.
So ABC.ZIP and ABC.ARJ will be assumed to be dupes.
<NAME.EXT> will check for files where the full name is the same.
NOTE
The dupe check has to be activated by command line parameter -D!
DupeCheck Name
┌───────────────────╖
│ Semaphore Control ╠════════════════════════════════════════════════════════
╘═══════════════════╝
┌──────────────
│ SemaphoreIdle <d:\path\filename.ext>
└─────────────────────────────────────────
Multiple usage possible
MaxList will watch the file names specified here. When one of the given
files is found, MaxList will stop processing, until the file is deleted.
SemaphoreIdle %Task3%
SemaphoreIdle %TaskMax1%
SemaphoreIdle %TaskMax2%
SemaphoreIdle %TaskMax3%
┌─────────────
│ SemaphoreRun <d:\path\filename.ext>
└─────────────────────────────────────────
This file is created by MaxList at startup and removed at end.
Other programs may check for the existance of this file and react
accordingly.
SemaphoreRun %Task0%
┌───────────────────────────────╖
│ Path and Name of Controlfiles ╠════════════════════════════════════════════
╘═══════════════════════════════╝
┌────────────
│ MaxAreaFile <d:\path\Filename.ext>
└─────────────────────────────────────────
Multiple usage possible
Specify all your FILEAREA.CTL files here, which MaxList has to process.
All *.CTL files which are included by Maximus INCLUDE statement are
processed automatically by MaxList, DO NOT SPECIFY THESE HERE!
The includes may be nested up to 10 levels in depth.
MaxAreaFile D:\MAX\FILEAREA.CTL
┌─────────────[v2.20]
│ MaxIndexFile <d:\path\Filename.ext>
└─────────────────────────────────────────
This entry is only necessary, when you want create announcelists.
In this case, you must enter the full path an name of Maximus indexfile.
Normaly this is MAXFILES.IDX.
MaxIndexFile d:\max\maxfiles.idx
┌─────────────[v2.20]
│ EchoTossLog <d:\path\Filename.ext>
└─────────────────────────────────────────
This entry is only necessary, when you want to write announces directly
to the Squishbase and your Echomailtosser need it.
MaxList store a entry for each Echotag, where a mail is written in, to
this file.
EchoTossLog d:\Bink\Log\EchoToss.Log
┌──────────────[v2.20]
│ ClMaxReqIndex <Yes | No>
└─────────────────────────────
A new Requestprocessor (CLMAXREQ) for the Mailer CANTALOUP is also
available from 'Home of MaxList'. This Requestprocessor use the FArea.dat
from Maximus 3.xx. By this, it's not necessary to create a Maximus 2
compatible Area.dat for each day.
MaxList can create a special index for the descriptions. This index
(FILES.CMX) is used by my Requestprocessor CLMAXREQ. It's not necessary,
but speedup requestprocessing, especially at great files.bbs.
HINT!
On DEBUGG Yes, no index is created and exist files are deleted!
ClMaxReqIndex No
┌─────────────[v2.20]
│ ExternEditor <d:\path\Filename.ext>
└─────────────────────────────────────────
Here you can enter a editor as you want. They is called, whenever a
FILE_ID.DIZ is imported and MaxList ist started wiht the -M switch.
So you can edit the description, before it's inserted into list and
files.bbs.
OS2 ExternEditor E.EXE
DOS ExternEditor C:\NC\MVE.EXE
┌─────────────
│ SortAreaFile <NONE | AREA | GROUP | BOTH>
└───────────────────────────────────────────────
SortAreaFile specifies how to sort the entries in the FILEAREA.CTL file.
The control file itself is not altered.
NONE - no sort at all
AREA - only area names are sorted numerical and alphabetical
GROUP - only group names are sorted numerical and alphabetical
BOTH - sort both area and group names
SortAreaFile Both
┌────────────────────────╖
│ Areaselective Settings ╠═══════════════════════════════════════════════════
╘════════════════════════╝
┌──────────
│ NoProcess AREA <Area[ .. Area]>
│ NoProcess FILE <Filearea.ctl>
└────────────────────────────────────────
Multiple usage possible, wildcards allowed
Excludes the listed areas or a specific FILEAREA.CTL from processing.
Every entry matching the given parameters is completely ignored.
ifn Special
NoProcess File FileArea.cd
NoProcess Area CD.0..CD.99
EndIf
┌─────────
│ Noformat <Area[ .. Area]>
└───────────────────────────────────
Multiple usage possible, wildcards allowed
This statement allows to suppress the FORMAT feature for FILES.BBS files
for the specified areas.
If you have long descriptions in your FILES.BBS files, you have to
specify NOFORMAT, if these entries should not be changed.
Otherwise MaxList will handle the descriptions as given in the @FORMAT
keyword at @FILEDESC.
! IMPORTANT HINT !
──────────────────
In areas, which have a 'NoFormat', the FILES.BBS files are NEVER changed.
By this, only a 'CreateLongDesc' will make modifications on the files.bbs!
NoFormat Listen.Text
┌───────────────
│ CreateLongDesc <Area[ .. Area]> <Maxlen>
└─────────────────────────────────────────────
Multiple usage possible, wildcards allowed
With this token, you can create longdescriptions.
In this, MaxList will remove all grafical characters, duplicated blank
and any multiple chars, which normaly used as framecharacters.
The product is plain Ascii. The maximum lenght of this text can be
limited. Furthermore, you can arrange this text in one or multiple line.
This procedure works areaseletive.
Following parameters you can use:
<Area [ .. Area]> denotes one or more areas.
<MaxLen> could use in a range of 0 up to 8192. When you use a
lenght of 0, the text is not truncated, until it's
less than 8192 bytes (after processing).
HINT!
When you have defined a 'NoFormat' for the correspondig areas, MaxList
will put the description in ONE line! Otherwise, the text is reformatted
to borders as defined in your BBS-Template by @FileDesc(left, right).
CreateLongDesc * 1024
┌───────
│ NoSort <Area[ .. Area]> <FILE | LIST | BOTH>
└─────────────────────────────────────────────────────────
Multiple usage possible, wildcards allowed
Excludes the given areas from sorting their file entries in the FILES.BBS
and/or the file lists.
FILE - Do not sort the corresponding FILES.BBS files
LIST - Do not sort in the file lists
BOTH - No sort at all (for the given areas)
NoSort 100 BOTH
┌───────────────────
│ SortBetweenComment <Area[ .. Area]>
└──────────────────────────────────────
With this, you can change the sortmethode of MaxList.
The marked areas will be sorted as long as a commentline will be
recognized. After that line, the sorting will restart from this postion.
The commentline stays therefore always at the pretend position.
HINT!
New files, which are added by AddOrphan, will be sorted in the block
afterward the last commentline.
For all NOT marked areas, the sortmethode is executed in normaly mode.
That is, a comment will be allways put in order to the next file and it
will sort corresponding.
SortBetweenComment *
┌─────────────
│ FreeDownLoad AREA <Area[ .. Area]> <TIME | BYTE | BOTH>
│ FreeDownLoad FILE <Filename.ext> <TIME | BYTE | BOTH>
└───────────────────────────────────────────────────────────────
Multiple usage possible, wildcards allowed
This statement will add Maximus switches /t, /b or /tb for free download
and/or free time to the FILES.BBS entries of the given areas or files.
The parameters specified here will be used when processing a @FEEDWNLD
token in a BBS template file.
TIME - Add /t to metching FILES.BBS entry
BYTE - Add /b to matching FILES.BBS entry
BOTH - Add /tb to matching FILES.BBS entry
FreeDownLoad Area 100 Both
┌──────────────
│ RemoveOldFile <Area[ .. Area]> <days> <BackupPath[\!A | \!P]>
└──────────────────────────────────────────────────────────────────
Multiple usage possible, wildcards allowed
Files older than <days> will be removed from your file base.
The files and the corresponding FILES.BBS entry are moved to <BackupPath>.
Options:
\!A - BackupPath gets extended by the area tag.
If your area is called GAMESNET100, <BackupPath> gets extended by
\GAMESNET.100. Area tags longer than 12 characters are truncated.
\!P - BackupPath gets extended by the last pathname specified in UPLOAD.
If you have set UPLOAD D\BBS\LISTS\, BackupPath> gets extended
by \LISTS.
NOTE
Areas of type CD or DATELIST will never be processed, i.e. RemoveOldFile
has no result.
RemoveOldFile 680..691 22 D:\BBSOLD\NODELIST
┌──────────────
│ ExcludeRemove AREA <Area[ .. Area]>
│ ExcludeRemove FILE <Filename.ext>
└────────────────────────────────────────
Multiple usage possible, wildcards allowed
Files placed in AREA or files matching FILE will never be moved, even if
matching the values of RemoveOldFile.
ExcludeRemove FILE Test.*
┌──────────────
│ RemoveOffLine <Area[ .. Area]> [LIST]
└─────────────────────────────────────────────
Multiple usage possible, wildcards allowed
Removes entries in the FILES.BBS where the corresponding file is missing.
If option LIST is specified, they will only suppressed in the file lists.
In this case, the FILES.BBS is not changed.
NOTE
Areas of type CD or DATELIST will NEVER be processed, also you have
a NoFormat assigned to the area.
RemoveOffline *
┌───────────────
│ AddOrphanFiles <Area[ .. Area]>
└───────────────────────────────────
Multiple usage possible, wildcards allowed
Adds automatically files of the specified areas, where no entry in the
FILES.BBS is present.
MaxList tries to extract a FILE_ID.DIZ from the archive and use that for
the description. If that is not possible, the string specified at
NODESCRIPTION will be used, except when command line parameter -M is
given. In this case MaxList will start the editor and wait for the user
to enter the description. When savin with F3 MaxList will add the entered
description as FILE_ID.DIZ to the archive.
AddOrphanfiles *
┌───────────────
│ NoAutoAddFiles <Area[ .. Area]> <Filename.Ext>
└─────────────────────────────────────────────────────
Multiple usage possible, wildcards allowed
Excludes file(s) from automatic adding, when found in <Area>.
NoAutoAddFiles 100 Treff.*
┌──────────
│ BBSHeader <Area[ .. Area]> <d:\path\Template.ext>
└─────────────────────────────────────────────────────────────
Multiple usage possible, wildcards allowed
Specify the FILES.BBS template for an area here.
If no template is given, an internal template is used.
BBSHeader * %Template%\BBShdr2.tpl
┌──────────────
│ HdrInEmptyBBS <Yes | No>
└─────────────────────────────
MaxList can write a hearder into the files.bbs, even if this area
contains no files. If it is switched to YES, MaxList will write the
BBSHeader into the FILES.BBS, if a template assigned.
HdrInEmptyBBS Yes
┌───────────────
│ WriteBBSTypeCD <Yes | No>
└─────────────────────────────
Support for Maximus 3.0 - TYPE CD.
Over this switch you can select, wheater MaxList write files.bbs for
areas which are marked with TYPE CD.
When you use NO, no files.bbs will be written.
WriteBBSTypeCD No
┌───────────────
│ NoWriteFileBBS <Area[ .. Area]>
└───────────────────────────────────
Multiple usage possible, wildcards allowed
Same as previouse, for Maximus 2.x users.
With this token you can select, in which areas MaxList should NOT write
the files.bbs new.
NoWriteFileBBS CD.*
┌──────────
│ UserLevel <Area[ .. Area]> <Level/Keys> <ReplaceString>
└──────────────────────────────────────────────────────────────────
Multiple usage possible, wildcards allowed
Use this statement to translate Maximus level/keys into a string
(e.g. the one you use in your box). The strings are used in the templates
at @AreaAcs / @GroupAcs.
UserLevel 1?? Twit/* Guest
UserLevel 200..679 Twit/* New User
UserLevel 692..899 Twit/* New User
UserLevel 680..691 Twit/* Point
UserLevel * Limited Normal
UserLevel * Worthy/p Point
UserLevel * AsstSysop CoSysop
┌────────────────────────────────╖
│ OKFiles for file request lists ╠═══════════════════════════════════════════
╘════════════════════════════════╝
All Okfiles (request lists) are defined in a block.
You may create several lists by entering the block several times. Note
that the file names (without extension) for a list have to be unique then!
Entries like SHUTTLE.KNW and SHUTTLE.UNK are NOT allowed!
MaxList will create temporary files with extension .OK# during processing.
When finished, the files are renamed to their desired name. This behaviour
allowes file requests beeing processed when MaxList is running.
Every block starts with OKFILE <d:\path\filename.ext>
and ends with END OKFILE
Between these two instructions additional keywords are necessary:
┌─────
│ MODE <SHORT | LONG | WILDCARD>
└────────────────────────────────────────
Specifies the type of the OKFile
Format SHORT: D:\PATH\
Format LONG: @FILENAME.EXT D:\PATH\FILENAME.EXT
Format WILDCARD: D:\PATH\*.*
┌────────
│ EXCLUDE <AREA | AREAACS | GROUPACS> <Parameter>
└──────────────────────────────────────────────────────
Optional. Multiple usage possible. Wildcards allowed.
Excludes areas or files by taking in to account:
AREA <Area[ .. Area]> - areas
AREAACS <Level/Keys> - level and keys of area
GROUPACS <Level/Keys> - level and leys of group
You may specify wildcards at all parameters. Note, that you ALWAYS have
to specify BOTH, i.e. level AND keys at xxxACS, e.g. Normal/p, */p or
Normal/*.
If you want to exclude the area BACK which is present in several groups,
you may do this by simply specifying EXCLUDE GFD.*.BACK
┌────────
│ INCLUDE <AREA | AREAACS | GROUPACS> <Parameter>
└──────────────────────────────────────────────────────
Optional. Multiple usage possible. Wildcards allowed.
Include areas previously excluded. Syntax is the same as EXCLUDE.
┌───────────[v2.20]
│ HEADERFILE <d:\Path\Filename.ext>
└─────────────────────────────────────
Optional. Multiple usage possible.
The file(s) specified by this entry are included at the beginning of
OkFile, in the order as they occur here.
┌──────────
│ MAGICFILE <d:\Path\Filename.ext>
└─────────────────────────────────────
Optional.
This file, was normaly contain your magic name definitions, is copied
to OkFile directly after all HeaderFiles.
┌───────────[v2.20]
│ FOOTERFILE <d:\Path\Filename.ext>
└─────────────────────────────────────
Optional. Multiple usage possible.
The file(s) specified by this entry are written at the end of OkFile,
in the order as they occur here.
Example OKFile:
───────────────
OkFile d:\Bink\Shuttle.Ok
Mode WildCard
HeaderFile Shuttle.ban
MagicFile d:\Bink\Shuttle.Mag
FooterFile d:\Bink\Shuttle.Ftr
Exclude Area Gif.*
Include Area Gif.DB*
Include Area Gif.Cars*
End OKFile
┌──────────────────────────╖
│ Definition of File Lists ╠═════════════════════════════════════════════════
╘══════════════════════════╝
┌─────────
│ FileList <d:\Path\Filename.ext> <ListType> [<Parameter>]
└─────────────────────────────────────────────────────────────────────
Every file list definition has to start with this entry.
<ListType> defines the type of list to generate. Dependant on the type
of the list, additional parameters may be necessary.
The different types in detail:
│ ALL [Name] - Allfiles list
└──────────────────────────────────────
If [Name] is specified, it will occur at token @ListTyp.
Default is ALLFILES.
│ NEW <Days> [Name] - Newfiles list
└──────────────────────────────────────
In this list only files younger than <days> days are taken into account.
If [Name] is specified, it will occur at token @ListTyp.
Default is NEWFILES.
│ PART [Name] - Part list
└──────────────────────────────────
Is a allfiles list. You may use this type in order to list only selected
areas. If [Name] is specified, it will occur at token @ListTyp.
│ REPORT [Name] - Statistical list
└─────────────────────────────────────────
You have to specify in the templates WHAT kind of data to be displayed.
If [Name] is specified, it will occur at token @ListTyp.
Default is REPORT.
│ DUPE [Name] - List of dupe files
└───────────────────────────────────────────
This list is only created when DUPECHECK is specified and MaxList is
started with -D option.
If [Name] is specified, it will occur at token @ListTyp.
Default is DUPES.
│ ORPHAN [Name] - List of automatic added files
└──────────────────────────────────────────────────────
This list is created only, MaxList has added new files by AddOrphan.
If [Name] is specified, it will occur at token @ListTyp.
Default is ORPHAN.
│ ANNOUNCE [Name] - List of files, which not exist in MAXFILES.INX
└───────────────────────────────────────────────────────────────────────
This list is allways deleted at the start of MaxList. A new list is
created, whenever MaxList found a file, was not exist in Maximus index.
If [Name] is specified, it will occur at token @ListTyp.
Default is ANNOUNCE.
┌───────────────────────────────────────────┐
│ Parameter inside a list definitions block ├───────────────────────────────
└───────────────────────────────────────────┘
│ ArchiveList <ArchiverName> [d:\Path\filename]
└──────────────────────────────────────────────────────
Specifies the compressor and the file name of the list.
<ArchiverName> is the type of compressor defined in the archiver
definition (ARCHIVER <type>)
│ ListHeaderFile <d:\path\Filename.ext>
└─────────────────────────────────────────
Multiple usage possible
The file(s) specified by this entry are included at the beginning of
the list, in the order as they occur here.
You may use this to include your logo file and others.
Then the title template is following.
│ ListFooterFile <d:\path\Filename.ext>
└─────────────────────────────────────────
Multiple usage possible
The file(s) specified by this entry are included at the end of the list,
in the order as they occur here and immeditately after the report footer.
Then my copyright notice is following.
│ ListTitle <TemplateDatei>
└──────────────────────────────────
After the header file you may insert a title in the list, eg. the list
type (ALLFILES, NEWFILES a.s.o.)
Output is dependant on what you have specified in the template.
│ AreaHeader <TemplateDatei>
│ AreaFooter <TemplateDatei>
└──────────────────────────────────
AreaHeader: Header and format definition for areas.
AreaFooter: Footer for areas.
For details see TEMPLATE.DOC
│ GroupHeader <TemplateDatei>
│ GroupFooter <TemplateDatei>
└──────────────────────────────────
GroupHeader: Header and format description for groups in the summary.
GroupFooter: Footer for groups.
For details see TEMPLATE.DOC
│ ReportHeader <TemplateDatei>
│ ReportFooter <TemplateDatei>
└──────────────────────────────────
ReportHeader: Header for the statitics at the end of the list.
ReportFooter: Issued before ListFooter.
For details see TEMPLATE.DOC
│ AllAreaReport <Yes/No>
└───────────────────────────
NO: no statistics (report) is added to the list.
This keyword has no effect at report lists. Of course ;-)
│ Exclude <AREA | FILE | AREAACS | GROUPACS> <Parameter>
└──────────────────────────────────────────────────────────────────
Optional. Multiple usage possible. Wildcards allowed
Excludes areas or files by taking into account:
AREA <Area[ .. Area]> - areas
FILE <FileName.ext> - files
AREAACS <Level/Keys> - level and keys of area
GROUPACS <Level/Keys> - level und keys of group
You may specify wildcards at all parameters.
When files are excluded, a comment in FILES.BBS following after that
file will not be included in the list.
Note, that you ALWAYS have to specify BOTH, i.e. level AND keys at
xxxACS, e.g. Normal/p, */p or Normal/*.
If you want to exclude the area BACK which is present in several groups,
you may do this by simply specifying EXCLUDE GFD.*.BACK.
│ Include <AREA | FILE | AREAACS | GROUPACS> <Parameter>
└──────────────────────────────────────────────────────────────────
Optional. Multiple usage possible. Wildcards allowed
Include areas or xxxACS previously excluded.
Syntax is the same as EXCLUDE.
───────────────────────
!! ANNOUNCELIST ONLY !!
───────────────────────
Inside your announcelist the follow parameters are nescessary, if you
want to write this list directly as a Echomail to your Squishbase:
┌──────────[v2.20]
│ SqishMail <YourAka> <EchoTag> <d:\Path\squishFile>
└─────────────────────────────────────────────────────────────
<YourAKA> - Your nodenumber (Zone:Net/Node[.point])
<EchoTag> - The name of this echo, e.g. NEWFILES.GER
<d:\path\SquishFile> - Path and name of .SQD file for this echo
│ MsgHeader "<From>" "<To>" "<Subject>"
└──────────────────────────────────────────────────
This strings are written to the messageheader. Each parameter must be
enclosed in double quote, e.g "xyz" and separate by blanks.
│ MsgOrigin <String>
└─────────────────────────
Origin of your message. MaxList will allway create a origin in follow
format: * Origin <String> (<YourAKA>)
┌────
│ END FileList
└───────────────
Needed at the end of every file list definition block
┌───────────────────────┐
│ Example ALLFILES List ├────────────────────────────────────────────────────
└───────────────────────┘
FileList %MxLDir%\24442050.ALL All
ArchiveList Zip %ListDir%\2050all
ListHeaderFile %MxLDir%\SHUTTLE.HDR
ListTitle %Template%\Title.tpl
AreaHeader %Template%\Areahdr2.tpl
ReportHeader %Template%\Reprthdr.tpl
GroupHeader %Template%\GroupHdr.tpl
AllAreaReport Yes
Exclude Area 900..989
Exclude Area 999
Exclude AreaAcs Extra/*
Exclude AreaAcs */P
End FileList
┌───────────────────┐
│ Example PART List ├────────────────────────────────────────────────────────
└───────────────────┘
FileList %MxLDir%\24442050.WOS Part WOS-NET
ArchiveList Zip %ListDir%\2050wos
ListHeaderFile %MxLDir%\SHUTTLE.HDR
ListTitle %Template%\Title.tpl
AreaHeader %Template%\Areahdr2.tpl
ReportHeader %Template%\Reprthdr.tpl
GroupHeader %Template%\GroupHdr.tpl
AllAreaReport Yes
Exclude Area *
Include Area 400..469
End FileList
┌───────────────────────┐
│ Example NEWFILES List ├────────────────────────────────────────────────────
└───────────────────────┘
FileList %MxLDir%\24442050.NEW NEW 14
ArchiveList Zip %ListDir%\2050new
ListHeaderFile %MxLDir%\SHUTTLE.HDR
ListTitle %Template%\Title.tpl
AreaHeader %Template%\Areahdr2.tpl
ReportHeader %Template%\Reprthdr.tpl
GroupHeader %Template%\GroupHdr.tpl
AllAreaReport Yes
Exclude Area 900..989
Exclude Area 999
Exclude AreaAcs Extra/*
Exclude AreaAcs */P
End FileList
┌────────────────────────────────────┐
│ Example NEWFILES List for QWK User ├───────────────────────────────────────
└────────────────────────────────────┘
FileList D:\MAX\OLR\NEWFILES.DAT New 7
ListHeaderFile %MxLDir%\SHUTTLE.HDR
ListTitle %Template%\Title.tpl
AreaHeader %Template%\Areahdr2.tpl
ReportHeader %Template%\Reprthdr.tpl
GroupHeader %Template%\GroupHdr.tpl
AllAreaReport No
Exclude Area 900..989
Exclude Area 999
Exclude AreaAcs Extra/*
Exclude AreaAcs */P
End FileList
┌───────────────────┐
│ Example DUPE List ├────────────────────────────────────────────────────────
└───────────────────┘
FileList %MxLDir%\24442050.DUP Dupe
ListTitle %Template%\Title.tpl
AreaHeader %Template%\DupeHdr.tpl
ReportHeader %Template%\Reprthdr.tpl
GroupHeader %Template%\GroupHdr.tpl
AllAreaReport Yes
Exclude Area 900..989
End FileList
┌─────────────────────┐
│ Example ORPHAN List ├──────────────────────────────────────────────────────
└─────────────────────┘
FileList %MxLDir%\24442050.ORP ORPHAN AutoAdd
ListTitle %Template%\Title.tpl
AreaHeader %Template%\Areahdr2.tpl
ReportHeader %Template%\Reprthdr.tpl
GroupHeader %Template%\GroupHdr.tpl
AllAreaReport Yes
End FileList
┌───────────────────────┐
│ Example ANNOUNCE List ├────────────────────────────────────────────────────
└───────────────────────┘
FileList %MxLDir%\24442050.ANN ANNOUNCE
AreaHeader %Template%\Areahdr2.tpl
AllAreaReport No
SquishMail 2:2444/2050 Shuttle_Announce i:\mail\shuttle\sht_Anno
MsgHeader "Wilfried Brinkmann" "All Points" "New files"
MsgOrigin Lets go, is nearly free ;-)
Exclude Area Upload
End FileList
══════════════════════════════════════════════════════════════════════════════
Wilfried Brinkmann, FidoNet 2:2444/2050 Hattingen, February 1996
══════════════════════════════════════════════════════════════════════════════